Hi Jeff. I am unable to replicate this because I cannot figure out how to configure extra fields to users.
I do see the user table has the extra column, how would I go about enabling this?
Code looks good.

Yeah, I wasn't surprised that this bug didn't get caught because this feature never got documented and I imagine not many are using it.

You can enable extra profile fields by configuring them in the organization.features column in the database. For example:

{ 
   "profile_fields": [
        {
            "label": "Affiliate",
            "name": "affiliate"
        },
        {
            "label": "Local Number",
            "name": "local"
        }
    ]
}

Possibly, you might need to populate the fields for a use and then edit again in order to trigger the bug.

Also worth noting that there's an old open PR from WFP #1961 that does add a UI for configuring fields along with other improvements, but it would need a rebase and testing.